Subject: Registration flows

From: Dave Finnie <[email-masked]>
Date: Wed, 8 Nov 1995 12:00:59 +1100

We have just hit an interoperability problem against VTAM 4.3 that we
did not have against VTAM 4.2, and wanted some input about who needs
to change:

In our register (EN->NNS) we always include a X'3C' CV with resource
type X'F4' and our ENCP name.

If this is the first register after connecting to the NNS, we also
include X'3D' CV with resource type X'F3' and our ENCP name (along
with our other local LUs defined at that point).

While this works against VTAM 4.2, we now receive sense 1014023c from
VTAM 4.3, meaning:

> Conflicting directory entry or invalid Associated Resource Entry
> (X'3C') control vector.

I know that SNA Formats indicates that the 3C/F4 and 3D/F3 combination
can be combined into a 3D/F4 CV, however we experienced problems in
the connectathons of the past where some nodes required the presence
of a 3C CV. Unfortunately I can't remember which ones, or how many :-)

Could the architecture group please let us know a recommended approach
to this problem ?

Thanks,

Dave